Updated the operator deployment README with a custom example. Include 0.2.8. #1487
Conversation
|
@claude Can you please bump the operator chart by a fix version. Make sure to follow the bumping instructions in the |
|
Claude encountered an error —— View job I'll analyze this and get back to you. |
|
Ahh I just realised Claude doesn't work on forked branches. @RoddieKieley You'll have to bump up the Charts manually I'm afraid :( |
RoddieKieley
force-pushed
the
custom-helm-chart-values-README-update
branch
from
e89b543 to
95e3303
Compare
…art version. Signed-off-by: Roddie Kieley <[email protected]>
RoddieKieley
force-pushed
the
custom-helm-chart-values-README-update
branch
from
95e3303 to
d44588c
Compare
|
I think @jhrozek was correct that the changes to values-openshift.yaml made it into main elsewhere as when I rebased on main I was just left with the update to the README.md and the README.md.gotmpl file updates. Being a bit new to this workflow I also had still missed the separate bump from 0.2.5 to 0.2.6, which should also now be resolved as per the checks passing atm. @JAORMX apologies for making your thumbs up quickly stale and having to re-request the review. |
Small update to include a reference on how to use a custom values file to install via helm chart. References the newly included values-openshift.yaml which has been bumped to include the latest released version of the operator 0.2.8.
Open question; for the custom values file, values-openshift.yaml in this case, how should it be referenced to be consistent with other README's and the docs?
./values-openshift.yaml (assuming it's in the current dir but being explicit)
values-openshift.yaml (also assuming it's in the current directory but implicit)
./deploy/charts/operator/values-openshift.yaml (assuming one has cloned the repo and is in the root of the project)
raw github ref?
Please feel free to update as required.